-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: bump viem to 1.6.0 #1308
feat: bump viem to 1.6.0 #1308
Conversation
🦋 Changeset detectedLatest commit: db79b4e The changes in this PR will be included in the next version bump. This PR includes changesets to release 27 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
return /already known|nonce too low/.test(String(error)); | ||
return ( | ||
error instanceof BaseError && | ||
error.walk((e) => e instanceof NonceTooLowError || e instanceof NonceTooHighError) != null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for context, when is a NonceTooHighError
triggered? Shouldn't it be possible to submit nonces with gaps / would viem error in that case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
honestly not sure how to trigger this, but I assume it's in viem because it's in the geth source: https://github.com/search?q=repo%3Aethereum%2Fgo-ethereum+ErrNonceTooHigh&type=code
and seemed like a good case to re-fetch the current nonce from the chain before retrying
fixes #1276
fixes #1262